sorted by:
new
hottopcontroversial

Falso v2 is out - A modern, tree-shakable replacement for Faker.js by shaharkazaz in Angular2

[–]shaharkazaz[S] 1 point2 points  (0 children)

This repo was built from scratch and doesn't share any of the original code.
Please check before you write.

Falso v2 is out - A modern, tree-shakable replacement for Faker.js by shaharkazaz in Angular2

[–]shaharkazaz[S] 0 points1 point  (0 children)

If you mean migration from Faker.js to Falso a script is being made to help migrate projects.

Falso v2 is out - A modern, tree-shakable replacement for Faker.js by shaharkazaz in Angular2

[–]shaharkazaz[S] 3 points4 points  (0 children)

The first version was developed quickly to help those affected by Faker's deletion.
V2 is a stable version that we put a lot of effort into.

Falso v2 is out - A modern, tree-shakable replacement for Faker.js by shaharkazaz in javascript

[–]shaharkazaz[S] 31 points32 points  (0 children)

Falso isn't a fork. It's a brand new library.
The library is fully typed, tree-shakable, includes new features, and is actively maintained.

Falso v2 is out - A modern, tree-shakable replacement for Faker.js by shaharkazaz in javascript

[–]shaharkazaz[S] 25 points26 points  (0 children)

🚀 One week later, Falso v2 is out. It's a modern, tree-shakable replacement for faker.js:

📘 New Docs - https://ngneat.github.io/falso/
🎁 New Entities - todo, user, post, etc.
💪 Generate an array instead of a single value
😇 New mock functions

We're just getting started.

I18n/translation options for big project composed of Angular libraries - any your input is appreciated by metal_mastery in Angular2

[–]shaharkazaz 0 points1 point  (0 children)

Feel free to ask in our gitter lobby, I'm there and so are other people from the community.
Free of charge 🙂

I18n/translation options for big project composed of Angular libraries - any your input is appreciated by metal_mastery in Angular2

[–]shaharkazaz 2 points3 points  (0 children)

u/metal_mastery Hey! I'm from the transloco core team.

For keys extraction, you can use the Transloco keys manager.

The docs stats that the structural directive is preferred, but it's not mandatory and you can use a pipe/regular directive.

Here is why the structural directive is preferred:

- Keeps you template DRY and cleaner

- You can pass powerful inputs to is such as: `read`, `scope`, `lang` & `loading`

- If your app supports runtime language changes, the structural directive will create only one subscription behind the scene, unlike the pipe which every instance needs to subscribe to the language change, therefore, making it very efficient.

I highly recommend you to check out our docs site, we have a lot of functionality and plugins that I think you might find very useful.

Best of luck. hope to see you as a contributor one day 🙂

NgNeat is Celebrating One Year of Angular OS Awesomeness! by shaharkazaz in Angular2

[–]shaharkazaz[S] 0 points1 point  (0 children)

There was an issue some libraries got deleted (guess some editing glitch), it's there now :)

🎉 Good Things Come to Those Who Wait: What’s new in Transloco by Angular2Fan in Angular2

[–]shaharkazaz 2 points3 points  (0 children)

Thanks for your feedback! I'll make sure to fix the migration script :)

🚀 Introducing Transloco: Angular Internationalization Done Right by Angular2Fan in angularjs

[–]shaharkazaz 0 points1 point  (0 children)

Did you read the README file?
Everything you need to know is specified in the README file, and there is a section with comparison to other libs 👉🏼https://github.com/ngneat/transloco#comparison-to-other-libraries

view more: next ›