format
community-protocols
format | community-protocols | |
---|---|---|
19 | 8 | |
1,904 | 168 | |
0.8% | 0.0% | |
9.4 | 5.4 | |
3 days ago | 24 days ago | |
C# | ||
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
format
-
What We Need Instead of "Web Components"
C# has https://github.com/dotnet/format but because C# is, well, not JS, the importance of linting is far less significant. Instead, there are hundreds of out-of-box analyzers that highlight problematic patterns or likely mistakes in the code and there are even more that you can enable through extensions (like Roslynator) or through packages that are 'dotnet add package' away.
On the package management - it couldn't be more different between Java and C# and it's incorrect to compare the two. .NET has few if any issues of the former.
-
Enhancing Your Open-Source Project with Static Analysis Tools
In my project, I incorporated a source code formatter provided by the dotnet framework. I also added .editorconfig file to the root directory of my project. This file defines formatting rules, such as indent style and indent size, ensuring consistency throughout the codebase.
-
Rider - Formatting across projects
However: It would appear that dotnet has a lot of extension values for editorconfig - does Rider support all of those? Some of those? Is there documentation of any extension?
-
100% deterministic c# formatter
Like this post explains: https://github.com/dotnet/format/issues/879
-
Dotnet, C#, code format on JetBrain IDE Rider
Dotnet Format
-
Enforcing .NET code style rules at compile time
Oh, I'm using .net format. https://github.com/dotnet/format . I will take a look at csharpier to compare both :)
- Migrating from JS/TS ecosystem to Blazor
-
Which linters are you using for CI environments?
- dotnet format but this is not a linter I think?
-
[Avançado] Criando templates customizados em C#
Para formatar seu código instale o dotnet format e execute o seguinte comando:
-
How do you format?
dotnet format does not break lines when they get too long, or collapse lines if they are too short and could be fit on the same line. See https://github.com/dotnet/format/issues/246. Another way to say it - no matter where you put linebreaks in a given code file, csharpier will produce the same output. dotnet format would produce a different output based on where current line breaks exist.
community-protocols
-
What We Need Instead of "Web Components"
> except that "reactivity" does not meet the bar of developers collectively having landed on a solution to a common problem
Now that everyone seems to be in love with signals, there is work going on in the web components community group to prepare a spec for a signal (or observable, not sure what they are trying to call it) primitive [0]. It seems that they are getting ready to bring it to TC39 as a proposal.
(In the meantime, the Observable primitive from rxjs been given a go-ahead for browser implementation. There is a proposal ready [1], and I think I heard that it may already be in Chrome behind a flag [2].
So yeah; it's gonna be fun. Especially if both groups call their primitive Observable :-)
0 - https://github.com/webcomponents-cg/community-protocols/issu...
1 - https://github.com/WICG/observable
2 - https://nitter.net/BenLesh/status/1737174784406933599
-
Show HN: Hyphen – custom element base class for good ergonomics
The custom element spec definitely only deals with the mechanics of when are where to run your component's lifecycle code - it says nothing about data. So your choices are basically property accessors, which are interoperable, but require prop-drilling for global-ish data, or something proprietary like a state management library.
The Web Components Community Group (WCCG) is offering something of a third way with the community protocols: https://github.com/webcomponents-cg/community-protocols
The Context protocol provides tree-scoped ambient data in an interoperable way. It's implemented by Lit and FAST (I believe). It doesn't replace a data store, but it's often used to provide data stores to components, and at least reduce some coupling.
-
Events are the shit
Did you know events can also carry promises? A great showcase of this pattern is the Pending Task Protocol by the Web Components Community Group. Now, "Pending Task Protocol" sounds very fancy, but really, it's just an event that carries a promise.
-
Nx Console gets Lit
If you’re coming from the Angular world, you probably appreciate the great dependency injection (DI) mechanism they have. You can centrally define some services and reuse them across your app, without thinking about passing on props from component to component - the DI system takes care of it. Lit provides something similar via the [@lit-labs/context](https://lit.dev/docs/data/context/) package. It’s based on the Context Community Protocol and similar to React’s context API.
-
Back to the Front-end: Exploring the Future of the Umbraco UI (Part 9 - Context API)
Fundamentally it is an event based mechanism to access state or "context" from ancestores of a component node. Based on the Web Components Context Protocol RFC which in turn is inspired by React's Context Api, the key purpose is to solve the problem of prop drilling.
- 🕎 8 Days of Web Components Tips
-
JavaScript vs JavaScript: Round 2. Fight!
The conversation led to the creation of https://github.com/webcomponents-cg/community-protocols. So there is some effort to standardize at least on convention for these higher-order considerations, but working through this and how opinionated it is made me recognize even more that this has a lot of similarities to a different group building a different framework. Tricky balance.
-
We Use Web Components at GitHub
I’m pretty actively following a lot of the web components community so I thought I would jump in here with some hopefully helpful information. Depending on what you mean by SEO it’s worth noting that for a while now Google and I believe Bing and a few others haven’t had any kind of requirement to pre-render content. You can just serve standard web components or any kind of SPA style front end and it will get indexed just fine, no penalties and no real issues unless you’re doing something particularly strange.
However, one of the more exciting projects in the web components space (lit.dev) now also supports proper SSR as well which is a very new thing in the world of web components. They are trying to build it in such a way that any other library can take advantage of through a common interface.
In fact there are some kind of early stage talks happening over here https://github.com/webcomponents/community-protocols where a bunch of companies like Google, Adobe, ING and others are trying to develop some open protocols on a whole bunch of topics to improve interoperability between various libraries so that no one has to buy in 100% to any one setup.
What are some alternatives?
csharpier - CSharpier is an opinionated code formatter for c#.
web3-sign-msg - web3-sign-msg is a modern web component built with ficusjs to sign messages with your eth private key in Metamask
omnisharp-vscode - Official C# support for Visual Studio Code [Moved to: https://github.com/dotnet/vscode-csharp]
vscode-webview-ui-toolkit - A component library for building webview-based extensions in Visual Studio Code.
CodeMaid - CodeMaid is an open source Visual Studio extension to cleanup and simplify our C#, C++, F#, VB, PHP, PowerShell, JSON, XAML, XML, ASP, HTML, CSS, LESS, SCSS, JavaScript and TypeScript coding.
soci-frontend - [Moved to: https://github.com/jjcm/nonio-frontend]
StyleCopAnalyzers - An implementation of StyleCop rules using the .NET Compiler Platform
React - The library for web and native user interfaces.
prettier - Prettier is an opinionated code formatter.
services-as-dom-elements
dotnet-full-framework-ci-sandbox - This repository aims to show how to create GitHub Actions to: Build and Test a .Net Full Framework Web API project; Check the code formatting (.NET / C#); Run SonarQube code static analysis.
nx-console - Nx Console is the user interface for Nx & Lerna.