Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

window.faker on faker.dev website #2426

Closed
andylacko opened this issue Sep 25, 2023 · 4 comments · Fixed by #2544
Closed

window.faker on faker.dev website #2426

andylacko opened this issue Sep 25, 2023 · 4 comments · Fixed by #2544
Labels
c: docs Improvements or additions to documentation c: feature Request for new feature has workaround Workaround provided or linked p: 1-normal Nothing urgent s: waiting for user interest Waiting for more users interested in this feature
Milestone

Comments

@andylacko
Copy link

andylacko commented Sep 25, 2023

Clear and concise description of the problem

I couldn't test the lib in 60sec on the internet.

Suggested solution

Inspired by lodash.com. Just assign window.faker = faker on the faker.dev web and write console.info('You can test faker by accessing it here from console'). There will be the most up-to-date lib directly on you web to test.

image

Alternative

No response

Additional context

No response

@andylacko andylacko added c: feature Request for new feature s: pending triage Pending Triage s: waiting for user interest Waiting for more users interested in this feature labels Sep 25, 2023
@github-actions
Copy link
Contributor

Thank you for your feature proposal.

We marked it as "waiting for user interest" for now to gather some feedback from our community:

  • If you would like to see this feature be implemented, please react to the description with an up-vote (:+1:).
  • If you have a suggestion or want to point out some special cases that need to be considered, please leave a comment, so we are aware about them.

We would also like to hear about other community members' use cases for the feature to give us a better understanding of their potential implicit or explicit requirements.

We will start the implementation based on:

  • the number of votes (:+1:) and comments
  • the relevance for the ecosystem
  • availability of alternatives and workarounds
  • and the complexity of the requested feature

We do this because:

  • There are plenty of languages/countries out there and we would like to ensure that every method can cover all or almost all of them.
  • Every feature we add to faker has "costs" associated to it:
    • initial costs: design, implementation, reviews, documentation
    • running costs: awareness of the feature itself, more complex module structure, increased bundle size, more work during refactors

View more issues which are waiting for user interest

@ST-DDT
Copy link
Member

ST-DDT commented Sep 25, 2023

Workaround: https://fakerjs.dev/new

@ST-DDT ST-DDT added c: docs Improvements or additions to documentation has workaround Workaround provided or linked p: 1-normal Nothing urgent and removed s: pending triage Pending Triage labels Sep 25, 2023
@ST-DDT ST-DDT added this to the vFuture milestone Sep 25, 2023
@matthewmayer
Copy link
Contributor

The library is a bit heavyweight to load it just in case someone opens the console.

I think we could rename Ecosystem>StackBlitz to something like "Try it!"

@Jason-bolt
Copy link

Exactly right @matthewmayer, I believe the word Ecosystem is not clear for users to identify

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: docs Improvements or additions to documentation c: feature Request for new feature has workaround Workaround provided or linked p: 1-normal Nothing urgent s: waiting for user interest Waiting for more users interested in this feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants