Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Interactive card implemented using Vue and Typescript

typescript, vue, sass/scss
Katja Danilova•340
@katjadanilova
A solution to the Interactive card details form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


A small and interesting project to work on, and I decided to implement it using Vue. I incorporated additional form validation and made several UI adjustments, such as ensuring the bank card size was proportionate and adding a shake effect to the button. What was your solution for adding spaces in the card number field?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • S MD suleman•3,510
    @sulemaan7070
    Posted over 2 years ago

    hey Katja Danilova😄, congratulations on completing the challenge here are a few tips to make your site better..

    1.I see that you have used the body->flex but that property is causing extra space(margin) on the left and right sides...

    2.The validation seems very nice..The only thing which seemed like a bug is when I am entering the ii into the YY input field...there was no validation error..

    I really liked the button shaking-animation upon entering the wrong input great job, happy coding👍🏻🔥💯

    Marked as helpful
  • Katja Danilova•340
    @katjadanilova
    Posted over 2 years ago

    Do you have any ideas why do I get an error "Attribute modelvalue not allowed on element div at this point." in HTML validation report?

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub