vuejs/vue-router

Throw exception or provide info message when route's component is null

Open

#2038 opened on Jan 31, 2018

View on GitHub
 (9 comments) (0 reactions) (0 assignees)JavaScript (19,015 stars) (5,092 forks)batch import
contribution welcomefeature requestgood first issue

Description

What problem does this feature solve?

Currently, route's component can be null and it give no information and error. Provide information or raising error can help users to catch they have some import issues when they use

import * as components from './components'

export default [
  {
    path: '/accounts',
    component: components.AccountsListView,
    name: 'accountsListView'
  },
  {
    path: '/accounts/create',
    component: components.CreateEditAccounts,
    name: 'createAccounts'
  }
]

So if components.CreateEditAccounts is null, they will know what went wrong easier.

What does the proposed API look like?

Raise error when component is null or log info message.

Contributor guide

Tech stack
javascriptvue
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptVue Router basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Investigate the route configuration parsing logic in the vue router source, likely in `src/create matcher.js` or similar. Add a null check for the `component` property and either log a warning or throw an error with a descriptive message. Review the comments on the issue for any additional context or proposed solutions. Check existing tests to ensure no breaking changes.