Comments (4)
I had eslint doing cleanup on save in VSCode with all of the auto-formatting. I think you removed this file that enabled that:
Could we just re-enable that? Then this task is done and we do not need prettier.
from behave-graph.
Here is your commit where you removed this: 684df3d
from behave-graph.
I've added back auto-formatting via es-lint on save here: https://github.com/bhouston/behave-graph/blob/main/.vscode/settings.json
from behave-graph.
The problem with this approach is firstly that vscode settings file is a userland file and not really intended for sharing between developers (and obviously only works for people with vscode).
Secondly eslint is not really a code formatter, it can highlight code issues, but it's slightly out of scope to handle spacing, braces etc. That's where prettier comes in. Ideally we would use both, and let them do their own things.
from behave-graph.
Related Issues (20)
- Proposal - remove class-based node definition, replace with just JSON HOT 4
- Adopt Int32 as the integer type and Float64 as the floating point type. HOT 1
- Improve documentation HOT 2
- Move Scene Profile outside the core package HOT 2
- Update Flow with support for "configuration" on Sequence nodes HOT 1
- Proposal: Add Structured data support HOT 2
- Proposal: support union types HOT 2
- Improved Configuration to Support Documentation and Editors
- Website HOT 5
- Allow for external listeners/emitters for custom events
- Move category and label into metadata fields for node spec.
- Compatible nodes on drag to empty space HOT 1
- Scene node types not available HOT 1
- Move registry out of Flow.tsx into configuration that is passed in. Enables better customization
- Not implemented error and white screen
- opening nodepicker on bottom right of screen breaks background and viewport
- Change ILogger to have only a single function that takes severity and message. HOT 1
- Immutable state is problematic in async nodes like Delay HOT 2
- [Website] set/get variable nodes are not exposed to the React website HOT 1
- npx exec-graph ./graphs/core/flow/Branch.json gives error: '@behave-graph/scene@*' is not in this registry
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from behave-graph.